Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

[VMC on AWS] vCenter Cloud Gateway Appliance - Manually reset the MACHINE_SSL certificate (70630)

Last Updated: 11/7/2023Categories: How toTotal Views: 4730Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The vCenter Cloud Gateway Appliance (VCGA) certificate has expired. Updating the certificate through the VCGA UI is not possible or is not preferred.

Purpose

This is a manual procedure to update the RHTTPPROXY certificate on the vCenter Cloud Gateway for Hybrid Linked Mode (HLM).

Cause

The VCGA certificate has expired.

Resolution

This is the manual process to reset the MACHINE_SSL certificate for the vCenter Cloud Gateway Appliance:

Note: Ensure to take a powered off snapshot of the appliance before attempting below steps.

Extract the existing expired machine ssl certificate from the VECS store and save the copy to a file with name "old_cert.crt".

/usr/lib/vmware-vmafd/bin/vecs-cli entry getcert --store MACHINE_SSL_CERT --alias __MACHINE_CERT --output /tmp/old_cert.crt

Obtain the SHA1 fingerprint of the old cert, this is used later in Step 8.

openssl x509 -in /tmp/old_cert.crt -fingerprint -noout

Generate a public and private key pair for the new certificate and save them into files bearing names "priv.key" and "pub.key" respectively.

/usr/lib/vmware-vmca/bin/certool --genkey --privkey=priv.key --pubkey=pub.key

It is necessary to determine the on-prem vCenter that the vCenter Cloud Gateway Appliance was registered to during deployment. The output will be used for step 6 and the variable <FQDN of on-prem VC>. This can be accomplished using the following command:

/opt/likewise/bin/lwregshell list_values '[HKEY_THIS_MACHINE\Services\vmafd\Parameters]' | grep \"DCName\" | awk '{print $4}'|tr -d '"'

Modify the certool.cfg file to the requirements needed for the environment. Note: The Name and Hostname fields need to be the FQDN of the vCenter Cloud Gateway Appliance.

The certool.cfg file can be found here: /usr/lib/vmware-vmca/share/config/certool.cfg

Generate the new certificate using the following command that will invoke certool. Pass the private key file path to the "--privkey" parameter and save the resulting certificate generated to a file with name "new_cert.crt".

/usr/lib/vmware-vmca/bin/certool --gencert --privkey=priv.key --cert=new_cert.crt  --config=/usr/lib/vmware-vmca/share/config/certool.cfg --server=<FQDN of onprem VC>

Delete the existing machine ssl certificate from the VECS store.

/usr/lib/vmware-vmafd/bin/vecs-cli entry delete --store MACHINE_SSL_CERT --alias __MACHINE_CERT -y

Import the new machine ssl certificate and the corresponding private key into the VECS store.

/usr/lib/vmware-vmafd/bin/vecs-cli entry create --store MACHINE_SSL_CERT --alias __MACHINE_CERT --cert new_cert.crt --key priv.key

Invoke lookupservice to update ssltrust of the service registration endpoints with the newly generated certificate. This step is documented in detail here, https://kb.vmware.com/s/article/2121701. This is executed from the VCGA and the customer will supply the credentials.

python /usr/lib/vmware-lookupsvc/tools/ls_update_certs.py --url https://<FQDN of onprem VC>/lookupservice/sdk --certfile new_cert.crt --user '<[email-masked]>' --password '<password>' --fingerprint <sha1 hash of the old certificate to replace>

Workaround

If the VCGA UI is available, the certificate can be updated following this process: Replace the Certificate for the Cloud Gateway Appliance with Hybrid Linked Mode enabled

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
vRealize Automation postgres データベース ebs_event テーブルのパージ間隔を調整する方法 (70759)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
在 Enterprise PKS 群集中，API 服务器证书 configmap 包含证书链中的多个证书 (70603)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
vCenter Server Appliance 6.5 の VMDK のリスト - サイズ、マウント ポイントおよび目的 (70624)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud on Dell EMC

VMware Cloud on AWS

Related Versions:

Take Our Survey

Support Assistant